ActorTemplate: Enforce that all images must be pinned#51
Conversation
| @@ -0,0 +1,39 @@ | |||
| # Copyright 2026 Google LLC | |||
There was a problem hiding this comment.
Have you considered adding this validation as an XValidation in the CRD itself? The advantage is that it gets coupled to the CRD so there is no way to delete it. I don't know this, but I suspect error messages will be more precise too as the error is specific to the field.
There was a problem hiding this comment.
Good point. We need VAP for cross-field work, but this is scoped to a single field.
There was a problem hiding this comment.
Done, it seems to work.
406a125 to
fde1995
Compare
Julian Gutierrez Oschmann (juli4n)
left a comment
There was a problem hiding this comment.
You'll need to rebase on main and move this as the CRD types are under pkg/api/v1alpha1 now.
fde1995 to
ae07ae2
Compare
ae07ae2 to
ea40829
Compare
|
https://github.com/agent-substrate/substrate/actions/runs/26594400905/job/78361379429?pr=51
|
Should we set a limit in the number of containers on a given actor template spec? |
|
Uh, I thought I tested this locally, and saw it correctly rejecting images without '@' symbols. Maybe I had forgotten to remove the VAP? |
907f20b
907f20b to
fe0910c
Compare
|
OK, I've limited us to 10 containers. I also applied the check to the pause image, which has the same problem. |
fe0910c to
db2027e
Compare
This commit adds a ValidatingAdmissionPolicy that checks that all images in an ActorTemplate must be pinned to a specific hash.
Fixes #10